Configure Renovate - #1

Welcome to Renovate! This is an onboarding PR to help you understand and configure settings before regular Pull Requests begin.

🚦 To activate Renovate, merge this Pull Request. To disable Renovate, simply close this Pull Request unmerged.

📚 See our Reading List for relevant documentation you may be interested in reading.

🔡 Do you want to change how Renovate upgrades your dependencies? Add your custom config to renovate.json in this branch. Renovate will update the Pull Request description the next time it runs.

Detected Package Files

• conanfile.py (conan)
• .devcontainer/devcontainer.json (devcontainer)
• .devcontainer/ubuntu-conan-noble/devcontainer.json (devcontainer)
• .devcontainer/ubuntu-conan-resolute/devcontainer.json (devcontainer)
• .devcontainer/ubuntu-system-noble/devcontainer.json (devcontainer)
• .devcontainer/ubuntu-system-resolute/devcontainer.json (devcontainer)
• renovate.json (renovate-config)

Configuration Summary

Based on the default config's presets, Renovate will:

• Start dependency updates only once this onboarding PR is merged
• Hopefully safe environment variables to allow users to configure.
• Show all Merge Confidence badges for pull requests.
• Enable Renovate Dependency Dashboard creation.
• Use semantic commit type fix for dependencies and chore for all others if semantic commits are in use.
• Ignore node_modules, bower_components, vendor and various test/tests (except for nuget) directories.
• Group known monorepo packages together.
• Use curated list of recommended non-monorepo package groupings.
• Show only the Age and Confidence Merge Confidence badges for pull requests.
• Apply crowd-sourced package replacement rules.
• Apply crowd-sourced workarounds for known problems with packages.
• Ensure that every dependency pinned by digest and sourced from Forgejo contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from Gitea contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitHub.com and Github enterprise contains a link to the commit-to-commit diff
• Ensure that every dependency pinned by digest and sourced from GitLab.com contains a link to the commit-to-commit diff
• Correctly link to the source code for golang.org/x packages
• Link to pkg.go.dev/... for golang.org/x packages' title
• Provide a link to octochangelog's improved breakdown for Renovate's changelogs
• Wait until the npm package is three days old before raising the update. This a) introduces a short delay to allow for malware researchers and scanners to (possibly) detect any malicious behaviour in packages, and b) prevents the maintainer and/or NPM from unpublishing a package you already upgraded to, breaking builds.
• Rebase existing PRs any time the base branch has been updated.
• If automerging, push the new commit directly to the base branch (no PR).
• Automerge patch and minor upgrades if they pass tests.
• Pin github-action digests.
• Create at-most 8 commits and 2 PRs per hour per repository. But do allow an unlimited number of open PRs.
• Update version variables in dependencies.cpm.cmake
• Update go imports
• Do not upgrade perl version. See: https://github.com/renovatebot/renovate/discussions/23472 and https://github.com/renovatebot/renovate/discussions/23762
• Do not upgrade Ruby version version.
• Do no upgrade FluentAssertions to v8, https://github.com/cucumber/common/issues/2314
• Group related npm packages together to reduce thrashing
• Do not artificially delay updating npm packages from @cucumber
• Group related Maven packages together to reduce thrashing

What to Expect

With your current configuration, Renovate will create 1 Pull Request:

❓ Got questions? Check out Renovate's Docs, particularly the Getting Started section.
If you need any further assistance then you can also request help here.

This PR was generated by Mend Renovate. View the repository job log.